-
Notifications
You must be signed in to change notification settings - Fork 744
User Classification module documentation #9921
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -97,3 +97,7 @@ Therefore, the approach we take is to create a new non-persistable entity, `User | |||
{{< figure src="/attachments/deployment/general/populate-user-type/user-type-report.png" class="no-border" >}} | |||
|
|||
7. The report can be exported into an Excel file. | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this page needs a little bit more attention/love/rework.
What is important for customers to get clarity on the following options:
- userrole based (this is supported by User Classification)
- IdP-based user classification (this is described in current section 3.)
- custom (this is supported by user Classification module, or can be done as per old situation and which is described in section 4.
I think the ToC of this page should follow these options. That gives more an outside-in view - what is the logic I want to apply.
I'll send you a link to slide that explains how customers can choose from these options - it includes a decision tree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe for clarity this page should also say something about the deprecated method:
"Previously another method was supported: based on email address persisted in a custom user entity. This method involved the USAGE_METRICS_EMAIL_FIELDS as decribed here/link. This method is deprecated." (DRAFT)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this rework needs another separate PR. It should not hold the release of the User Classification module. I will create a separate PR for it.
https://mendix.atlassian.net/wiki/spaces/idx/pages/3795321043/User+Classification
Inputs from Jaap: https://mendix.atlassian.net/wiki/spaces/idx/pages/3650683342/Documentation+-+User+Classification+module+DRAFT